Remove codeql for staging#992
Conversation
|
Ooof actually the runners are tied up for over 3h 😱 |
|
I am going to manually kill the CodeQL jobs in |
|
@larsoner Thanks for reporting and for looking into this. I agree it’s safe for CodeQL not to be triggered on staging; running it on main should be sufficient for now. |
|
@larsoner, I have now introduced concurrency groups with cancel-in-progress: true. This should automatically cancel outdated runs when a newer run for the same branch/PR is triggered. That should reduce the number of long-running jobs blocking the queue while still allowing us to include staging. What do you think? |
We can try it! I'll keep an eye on the jobs and if they get backlogged consistently again we can revisit |
2 participants
Looking at https://github.com/mne-tools/mne-cpp/actions/workflows/codeql.yml I see 9 runners in the last 2h that will each be tied up for about an hour
This PR aims to reduce this usage by just running CodeQL on
main. I am not sure what the dev workflow is here exactly, but assuming you merge stuff fromstagingtomainoccassionally then this would help with the concurrency issues.Feel free to close and fix a different way, but it would be good to get something like this in ASAP so that other repo workflows can continue!